Mobile device cover for use with a host mobile device

ABSTRACT

A mobile application running on a host mobile device is used to control the display of notifications, received by the host mobile device, on a mobile device cover. The mobile device cover can run a different operating system than the host mobile device. The mobile device cover can also be assigned a different phone number than the host mobile device. Further, the mobile device cover can make or receive a phone call under the different phone number using its own cellular communication hardware.

FIELD OF THE DISCLOSURE

Certain embodiments of the disclosure relate to systems and methods forcontrolling a mobile device cover for use with a mobile device.

BACKGROUND OF THE DISCLOSURE

Conventional mobile phone covers are passive accessories to mobilephones. They can have static designs and can offer some measure ofprotection for the mobile phone.

Further limitations and disadvantages of conventional and traditionalapproaches will become apparent to one of skill in the art, throughcomparison of such systems with the present disclosure as set forth inthe remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE DISCLOSURE

Some embodiments according to the present disclosure relate to, forexample, an active cover for an electronic device or equipment asillustrated by and/or described in connection with at least one of thefigures, as set forth more completely in the claims.

Various advantages, aspects and novel features of the presentdisclosure, as well as details of an illustrated embodiment thereof,will be more fully understood from the following description anddrawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A shows an exemplary mobile device cover according to anembodiment of the present disclosure.

FIG. 1B shows a top view of an exemplary mobile device cover accordingto an embodiment of the present disclosure.

FIG. 1C shows a partially exploded side perspective view of an exemplarymobile device cover according to an embodiment of the presentdisclosure.

FIG. 1D shows an exploded side perspective view of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 1E shows an exemplary mobile device cover according to anembodiment of the present disclosure.

FIG. 1F shows a front side of a front portion of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 1G shows a front side of a middle portion of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 2 shows an exemplary circuit arrangement according to an embodimentof the present disclosure.

FIG. 3 shows an exemplary launch screen page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 4 shows an exemplary front page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 5 shows an exemplary connection page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 6 shows an exemplary instructions page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 7 shows an exemplary home page of a mobile application according toan embodiment of the present disclosure.

FIG. 8 shows an exemplary lightshows page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 9 shows an exemplary assigned contacts page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 10 shows an exemplary icons page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 11A shows an exemplary scrolling text page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 11B shows another exemplary scrolling text page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 12 shows an exemplary add item page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 13 shows an exemplary notifications-for-applications page of amobile application according to an embodiment of the present disclosure.

FIG. 14 shows an exemplary lighting-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 15 shows an exemplary lightshows-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 16 shows an exemplary icons-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 17 shows an exemplary battery page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 18 shows an exemplary lighting page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 19 shows an exemplary clock page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 20 shows an exemplary back design page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 21 shows an exemplary settings page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 22 shows an exemplary notifications-for-applications settings pageof a mobile application according to an embodiment of the presentdisclosure.

FIG. 23 shows an exemplary lightshows-for-contacts settings page of amobile application according to an embodiment of the present disclosure.

FIG. 24 shows an exemplary synchronization/reset page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 25A shows an exemplary preview as a portion of an exemplary page ofa mobile application according to an embodiment of the presentdisclosure.

FIG. 25B shows an exemplary preview page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 25C shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 25D shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 25E shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 26 shows an exemplary home screen displayed on a mobile devicecover according to an embodiment of the present disclosure.

FIG. 27 shows an exemplary phone page displayed on a mobile device coveraccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

As utilized herein the terms “circuit” and “circuitry” refer to physicalelectronic components (i.e., hardware) and any software and/or firmware(“code”) which may configure the hardware, be executed by the hardware,and/or otherwise be associated with the hardware. As utilized herein,“and/or” means any one or more of the items in the list joined by“and/or”. As an example, “x and/or y” means any element of thethree-element set {(x), (y), (x, y)}. As another example, “x, y, and/orz” means any element of the seven-element set {(x), (y), (z), (x, y),(x, z), (y, z), (x, y, z)}. As utilized herein, the term “exemplary”means serving as a non-limiting example, instance, or illustration. Asutilized herein, the terms “e.g.,” and “for example” set off lists ofone or more non-limiting examples, instances, or illustrations.

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of or provide one or morenon-limiting examples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

The drawings are of illustrative embodiments. They do not illustrate allembodiments. Other embodiments may be used in addition to or instead ofthe illustrative embodiments. Details that may be apparent orunnecessary may be omitted to save space or for more effectiveillustration. Some embodiments may be practiced with additionalcomponents or steps and/or without all of the components or steps thatare illustrated.

Some embodiments according to the present disclosure provide, forexample, suitable logic, circuitry, code, and/or combinations thereofthat may be adapted to perform the functions or acts described herein.

Some embodiments according to the present disclosure may relate to, forexample, systems and methods that provide an active cover for anelectronic device or equipment. Some embodiments contemplate that theactive cover and the electronic device or equipment can communicate(e.g., digitally communicate) with each other. Some embodimentscontemplate that the active cover and the electronic device or equipmentcan power themselves, for example, via direct current (DC) powersupplies (e.g., rechargeable batteries) and/or via alternating current(AC) power supplies (e.g., wall outlets). Some embodiments furthercontemplate that one or both of the active cover and the electronicdevice or equipment can power and/or recharge the other.

Some embodiments according to the present disclosure provide that theactive cover can sense when the electronic device is generating an alertor receiving a message, a notification, a call, an email, and/or anindication, and can provide an enhanced alert or indication (e.g.,audible and/or visual alert or indication) instead of or in addition tothe generated alert or indication of the electronic device. The activecover can provide a visual display (e.g., patterns of lights), displayinformation (e.g., a message, a notification, and/or an indication)received from the electronic device on a graphical user interface (e.g.,a touch-sensitive screen), generate a sound (e.g., voice, musical note,audible tone, etc.) and/or vibrate.

Some embodiments according to the present disclosure contemplate thatthe active cover includes a mobile device cover for use with, forexample, a host mobile device (e.g., a cellular handset, a cellulardevice, a smartphone, a wireless phone, a wireless device, a wirelesshandset, a multimode phone, a mobile phone compliant with multiplewireless communication standards, a mobile phone equipped with a globalpositioning system, a multiple-input-multiple-output phone, a wirelesscommunication device, a two-way radio, a communication device with oneor more antennas, etc.). The systems and methods disclosed herein canalso be used with, for example, tablets, tablet computers, laptops,computers, computing devices, and other devices as well. The systems andmethods can be used with stationary devices such as, for example,desktop computers and stationary monitors and/or displays as well. Someembodiments according to the present disclosure that the functionalityof the active cover can be directly implemented into the host mobiledevice, for example, as part of the housing of the host mobile device.

Some embodiments according to the present disclosure contemplate that,during a host mobile device alert or event, an active mobile devicecover can provide its own alert or indication according to signals(e.g., alert signals, indication signals, data, digital signals, etc.)received from the host mobile device. The active mobile device cover mayalso light in a distinct or random pattern such as, for example, anyarrangement, sequence, etc. using lights in which different colors,brightness, intensities, etc. form shapes, images, icons, emojis, text,alphanumeric text, video, messages, notifications, etc. that are eitherstatic or moving (e.g., animated), for example. The lights may beindividual or distinct lighting devices or may be part of or form atleast a portion of a screen or a display of the active mobile devicecover. In some embodiments, the distinct or random patterns can beilluminated according to the sound, sound signal, alert data, digitalsignal, and/or other information generated by the host mobile device,and received by the active mobile device cover, for example. In someembodiments, a distinct pattern can be assigned (e.g., manually by auser or automatically) to an associated sound, sound signal, alert,alert signal, digital signal, caller, contact, notification, etc.,and/or other information. For example, a distinct pattern can beassigned to a particular ring tone, ring tone signal, contactinformation (e.g., telephone number, email address, etc.), etc. A randompattern can be assigned to and/or associated with particular sounds,sound signals, alerts, alert signals, digital signals, callers,contacts, notifications, etc., and/or other information. For example, arandom pattern or selected pattern can be assigned to a particular ringtone or ring tone signal of the host mobile device, or to a particularsource (e.g., telephone number, caller ID, email address, IP address,etc.) of a message, email, call, etc. The random pattern can also beassigned to unassigned identifiers (e.g., telephone numbers, emailaddresses, IP addresses, source identifiers, etc.) or unrecognizedand/or unknown identifiers. In addition to enhancing the look and feelof the outside of the host mobile device, the active mobile device coverprovides the user with superior sensory input over the host mobiledevice alone, and/or protect the host mobile device from drops,scratches, etc.

Some embodiments according to the present disclosure provide a mobiledevice cover with lights such as light emitting diodes (LEDs) which canbe part of and/or form different types of displays (e.g., organic LED(OLED) screens, RGB LED screens, LCD displays, LED indicator lights,touch-sensitive displays, screens, etc.), or other light sources ordisplays.

Some embodiments according to the present disclosure provide a mobileapplication that runs on a host mobile device. The mobile applicationprovides a graphical user interface including one or more graphicalelements that are used to control the mobile device cover and the hostmobile device.

FIG. 1A shows an exemplary mobile device cover 100 according to anembodiment of the present disclosure. As shown in FIG. 1A, the mobiledevice cover 100 (e.g., a cover, a case, a shell, a protector, etc.) isphysically and/or electrically connected to a host mobile device 110. Insome embodiments, the mobile device cover 100 is wirelessly connected tothe host mobile device 110. In some embodiments according to the presentdisclosure, the host mobile device 110 (not shown in FIG. 1A except fora camera 125 and a sensor 135 on a back side 185 of the host mobiledevice 110) may be slipped inside or inserted into the mobile devicecover 100, or the mobile device cover 100 can be snapped on or stretchedaround, at least in part, or otherwise can be fit around, at least inpart, the host mobile device 110. FIGS. 1F and 1G show front sides of afront portion 145 and a middle portion 153 of the mobile device cover100 according to some embodiments of the present disclosure. Referringto FIGS. 1F and 1G, the host mobile device 110 (not shown) can beinserted or locked in between the guides 165 of the middle portion 153.Although some embodiments contemplate a via in the mobile device cover100 through which a female connector (e.g., a female USB-type connector)of the host mobile device can be accessed, other embodiments contemplatethe mobile device cover 100 with a connector 175 (e.g., a lightningconnector, a USB-type connector, a data connector, a rechargingconnector, multi-pin connector, etc.) that mates with the femaleconnector of the host mobile device 110 to provide a connection (e.g., apower connection, a physical connection, an electrical connection, asignal connection, a synchronization connection, etc.). In someembodiments, the connector 175 provides a connection (e.g., electricalconnection, data connection, etc.) between circuits in the host mobiledevice 110 and the mobile device cover 100. For example, the batteriesin the host mobile device 110 and the mobile device cover 100 can chargeeach other via the connector 175 and/or other ports, for example. Insome embodiments, the connector 175 is part of a connector assembly thatincludes a connector element 148, a coupler 149, and a port 147. Inaddition to or instead of the connector 175, the host mobile device 110and the mobile device cover 100 can communicate wirelessly (e.g.,Bluetooth communication, near field communication (NFC), other radiofrequency (RF) communication (e.g., Wi-Fi), infrared communication,etc.) with each other, as mentioned below. In some embodiments, thefront side 145 of the mobile device cover 100 can be interlocked withthe middle portion 153 of the mobile device cover 100 with the hostmobile device 110 there between. As noted before, the main display ofthe host mobile device 110 may or may not be covered by a transparentmaterial of the mobile device cover 100. In some embodiments, a window195 is provided in the front portion 145 of the mobile device cover 100so that the user can directly touch the display (e.g., touch-sensitivescreen) of the host mobile device 110.

In some embodiments, the mobile device cover 100 can be an accessory tothe host mobile device 110. In some embodiments, the mobile device cover100 can be an accessory that is operable while separate from the hostmobile device 110. The accessory can be in wireless communication withthe host mobile device 110. In some embodiments, the mobile device cover100 and the host mobile device 110 can be controlled via inputs (e.g.,buttons, touch-sensitive screens, capacitive touch, sliders, graphicalelements on graphical user interfaces, etc.) located on the mobiledevice cover 100, the host mobile device 110, a mobile applicationrunning on the host mobile device 110, a mobile application running onthe mobile device case 100, a wired and/or wireless signal sent to thehost mobile device 110, a wired and/or wireless signal sent to themobile device cover 100, etc. The wireless signal can include, forexample, Bluetooth signals, IEEE 802.11 signals, wireless local areanetwork (WLAN) signals, wireless personal area network (PAN) signals,Zigbee signals, infrared signals, RF signals, etc. sent to the mobiledevice cover 100, the host mobile device 110, etc. Accordingly, themobile device cover 100 and/or the host mobile device 110 include, forexample, antennas and circuits (e.g., processors, wireless hardware,transceivers, transmitters, receivers, etc.) to support wirelesscommunication between them 100, 110, and/or between the mobile devicecover 100, the host mobile device 110, and/or other wireless devices(e.g., wireless speakers, wireless microphones, wireless headphones,wireless earbuds, wireless displays, base stations, access points,wireless networks, etc.).

Referring to FIG. 1A, a back side 158 of the back portion 155 (e.g.,back cover) of an exemplary mobile device cover 100 according to anembodiment of the present disclosure is shown. The back portion 155 ofthe mobile device cover 100 has lights 160. The lights 160 can form, bea part of, and/or illuminate a screen (e.g., a main screen or display,indicator lights, light patterns, etc.) and can emit different colorswith different intensities at different times. The lights 160 can alsoform, be a part of, and/or illuminate another screen 132 or an extensionof the main screen along an edge 130 (e.g., a beveled edge, a chamferededge, a side, a lateral side, a border of the screen 162, etc.) of themobile device cover 100. Further, the lights 160 can illuminate beads180 with different colors as indicator lights, for example. The beads180 can be colored or not, and can be at least partially transparent,for example. In some instances, the beads 180 can take the configurationof letters, numbers, and/or shapes and can be flat or raised instructure. The beads 180 can be used as part of a Braille reader system,for example. In some instances, the beads 180 can include, for example,LED or light covers. In some examples, the beads 180 can be flattransparent plastic windows that can be positioned over lights 160. Insuch an instance, the beads 180 can be colored, and/or the lights 160can provide color through colorless, transparent beads 180. In someembodiments, the beads 180 can be disposed throughout the back cover 155of the mobile device cover 100 so that the beads 180 can be illuminatedin particular colors, patterns, and/or intensities at particular timesand/or in response to certain alerts or other information (e.g., digitalsignals, digital data, analog signals, etc.) received from the hostmobile device 110.

In some embodiments, when the host mobile device 110 and the mobiledevice cover 100 are operatively coupled, the mobile device cover 100can provide indicators and/or data (e.g., digital data, video data,streaming data, etc.) from the host mobile device 110 to the user viaoutput interfaces (e.g., lights, screens, speakers, etc.) of the mobiledevice cover 100. In some embodiments, when the host mobile device 110and the mobile device cover 100 are operatively coupled, the mobiledevice cover 100 and the host mobile device 110 are in one- or two-waydigital and/or analog data communication. The mobile device cover 100can display information, data, and/or content (e.g., multimedia content,video content, streaming content, social media content, scrolling text,etc.) received from the host mobile device 110. Further, the host mobiledevice 110 can display information, data, and/or content received fromthe mobile device cover 100. The host mobile device 110 and/or themobile device cover 100 can cause information, data, and/or content tobe displayed on the host mobile device 110. Further, the host mobiledevice 110 and/or the mobile device cover 100 can cause information,data, and/or content to be displayed on the mobile device cover 100. Theinformation, data, and/or content can be received from the host mobiledevice 110, the mobile device cover 100, another device, and/or a thirdparty, such as a mobile application, a website, etc. FIG. 1E shows anembodiment of the mobile device cover 100 in which the back cover 1030includes the lights 160 forming a touch-screen display 162 that can besimilar or the same as the display that can be shown on the main displayof the host mobile device 110. Thus, for example, the touch-screendisplay 162 of the mobile device cover 100 can operate in a same orsimilar manner (e.g., same or similar graphical user interface,graphical elements, touch-and-feel, etc.) as the main display of thehost mobile device 110. The touch-screen display 162 of the mobiledevice cover 100 can provide the same or similar array of icons 164 asthe main display of the host mobile device 110, for example, or can becompletely different. This can be useful, for example, if the display ofthe host mobile device 110 is being used for another purpose (e.g.,playing a video, taking a call, work use, personal use, etc.), but theuser wants to access other mobile applications. For example, the hostmobile device 110 can be used to operate a GPS navigation application,while the mobile device cover 100 is being used to watch a movie or tostream video. Further, since the host mobile device 110 and the mobiledevice cover 100 can be in wireless communication, the mobile devicecover 100 can be detached from the host mobile device 110 while watchingthe movie or streaming video, for example.

Referring to FIG. 1A, when the host mobile device 110 is receiving anincoming call, for example, beads 180 that form the word “CALL” on theback cover 155 of the mobile device cover 100 can be illuminated, causedto flicker, flash, etc. If a calendar event notification is activated orreceived by the host mobile device 110, for example, the beads 180 thatform the word “ALERT” can be illuminated, caused to flicker, flash, etc.If a text message is received by the host mobile device 110, forexample, the beads 180 that form the word “TEXT” can be illuminated,caused to flicker, flash, etc. These events and others (e.g., socialmedia postings or messages, changes in sports scores, news items,emails, SMS messages, etc.) can also be displayed on the touch-screendisplay 162. The beads 180 can also be illuminated different colors andwith different intensities to indicate different degrees of urgency. Forexample, if the alert is urgent (e.g., an email sent with “highimportance”), the beads 180 that form the word “ALERT” can flash redand/or with increased intensity to indicate urgency. In another example,if the incoming call or text message is not from an important person,which can be designated via programming, user settings, userconfigurations, user preferences, etc., the corresponding beads 180 canbe illuminated a dim blue. In some embodiments, the mobile device cover100 can determine the identity of the caller or the message sender viaelectrical signals, sound signals, acoustic signals, wireless signals,digital signals, etc. received from the host mobile device 110. In someembodiments, the host mobile device 110 can determine the identity ofthe caller or the message sender and send a data signal corresponding toand/or identifying the caller or the message sender to the mobile devicecover 100 as well as other information (e.g., voice mail, text message,indications of importance, etc.). Further, the user may be notified asto the name, number, email address, etc. of the sender or source of thealert, text, email, or other notification via the lights 160, beads 180,or other output devices (e.g., speakers, screens, vibration, etc.) ofthe mobile device cover 100.

In some embodiments, the mobile device cover 100 can be configured toprovide video (e.g., live streaming video, streaming video, storedvideo, etc.) and/or other information (e.g., digital data, messages,news, alerts, etc.) on one or more screens. The video can be providedvia the host mobile device 110, for example, or some other source towhich the mobile device cover 100 and/or the host mobile device 110 isoperatively coupled. For example, the mobile device cover 100 can haveits own wireless link with an access point (e.g., an IEEE802.11-compliant access point) or a base station (e.g., a cellular basestation, a portable base station, etc.) from which to download mediacontent. The mobile device cover 100 can also include memory storage(e.g., non-transitory memory storage, solid state memory storage,removable memory sticks, disks, cards, etc.) on which resides mediacontent for playing or displaying on the screen of the mobile devicecover 100 and/or the host mobile device 110. The video can be, forexample, stored on the host mobile device 110 or can be streamed via awireless link (e.g., cellular link, WIFI link, IEEE 802.11 link,wireless local area network (WLAN) link, Bluetooth link, RF link, etc.)with a content provider or a third party application. In someembodiments, closed captioning or subtitles can scroll along the mainscreen 162 which can include and/or be supplemented with one or morescreens 132 on one or more edges 130 of the mobile device cover 100. Insome embodiments, the mobile device cover 100 can be configured toprovide an alert of a received video message and to play the videomessage on the screen 162 of the mobile device cover 100. The screen 162of the mobile device cover 100 can be substantially independent or cansubstantially mirror the screen of the host mobile device 110. Thescreens 162, 132 can be incorporated into the housing of the electronicdevice. Further, the screen 162 of the mobile device cover 100 can betouch-sensitive and employ graphical elements of a graphical userinterface. Thus, for example, a user input via the touch-sensitivescreen 162 of the mobile device cover 100 can provide a user input tothe host mobile device 110 and/or the mobile device cover 100. Thescreen of the mobile device cover 100 can be set up to substantiallymirror the screen of the host mobile device 110 or to operateindependently of the screen of the host mobile device 110. Content ormaterial can also be displayed on the mobile device cover 100 and/or thehost mobile device 110 that is from an application on the host mobiledevice 110, for example. For example, if the user has access to a sportsapplication running on the host mobile device 110 that shows sportsvideos, television channels, movie channels, or live events on the hostmobile device 110, the video may be displayed on the host mobile device110 and/or the mobile device cover 100.

Some embodiments provide that digital signals can be received orprovided by the host mobile device 110 and forwarded to the mobiledevice cover 100 for storage, processing, and/or output (e.g., on adisplay, lights, a speaker, a vibrating mechanism, etc.). For example,in addition to multimedia data, some embodiments provide that data(e.g., alphanumeric data, indicators, control data, source information,etc.) can be received or provided by the host mobile device 110 andforwarded to the mobile device cover 100 for storage, processing, and/oroutput. For example, the edge screen 132 (or any other light 160 screenon the mobile device cover 100) can be configured to scroll informationrelating to news, sports, live or recorded events or movies, stocks,weather, calendar events, text messages, alerts, email, social mediamessages (e.g., messages or posts from mobile applications or websitessuch as Facebook, Twitter, Snapchat, Instagram, etc.), etc. In someembodiments, the information can scroll around one or more edge screens132 around the mobile device cover 100. In some embodiments, the hostmobile device 110 can be set to periodically receive or retrieve sportsdata (e.g., scores, news items, etc.) or other types of data. The datacan be from, for example, websites, mobile applications, other hostmobile devices, etc. The host mobile device 110 can send sports data,for example, to the mobile device cover 100; and the mobile device cover100 can display or scroll the data across the edge screen 132 of themobile device cover 100 or display or scroll on the screen 162. In someembodiments, the edge screen 132 can be touch-sensitive, therebyallowing the user to tap or swipe an email notification and read ascrolling email on the edge screen 132 or on another display (e.g., themain display 162 on the back cover 155) of the mobile device cover 100.In some embodiments, the data can flow across the edge screen 132 inresponse to a finger sweeping motion along the edge touch-sensitivescreen 132. In one embodiment, an incoming text message can be indicatedby the beads 180 forming the word “TEXT” being illuminated by lights160, the sender of the incoming text can be displayed on the edge screen132, and the text of the text message can be displayed on the mainscreen 162 on the back cover 155 of the mobile device cover 100. In oneembodiment, alphanumeric letters are displayed on the screen on the backcover 155 and the edge 130, either simultaneously or independently,indicating that a text message has been received and possibly displayingthe sender's name, the sender's associated icon, the sender's associatedimage (e.g., sender's picture), the sender's subject, the sender'sheader, the sender's body text, the sender's partial or full text, etc.A text or email icon can be displayed instead of the words TEXT, forexample. The display can also be a series of LEDs forming a grid toaccommodate lights show, scrolling text, etc.

The edge screen 132 can be configured to scroll completely or partiallyaround the mobile device cover 100 and/or along one or more of its edges130. In some embodiments, the edge 130 can be segmented or partitionedso that the right edge portion is reserved for a first subject (e.g.,stocks), the left edge portion is reserved for a second subject (e.g.,sports), the bottom edge portion is reserved for a third subject (e.g.,email), and the top edge portion is reserved for a fourth subject (e.g.,calendar items, alerts, etc.), for example. Within each segment, theedge screen 132 can scroll the data. In some embodiments, the user canprogram and/or select which subject is displayed on each individualsegment on the mobile device cover 100. In some embodiments, the usercan program the mobile device cover 100 so that it decides on whichsegment to display a particular subject (e.g., incoming call, incomingtext, incoming email, incoming message, mobile device notification,mobile device accessory notifications, music or other audionotifications, social media notifications, etc.).

FIG. 1B shows a top view of an exemplary mobile device cover 100according to an embodiment of the present disclosure. FIG. 1C shows apartially exploded side perspective view of an exemplary mobile devicecover 100 according to an embodiment of the present disclosure.

Referring to FIGS. 1B and 1C, the mobile device cover 100 can beadapted, for example, to provide physical vias (e.g., access openingsand windows) through which various input interfaces and outputinterfaces of the host mobile device 110 can be accessed withoutdetaching the mobile device cover 100 from the host mobile device 110.In some embodiments, the mobile device cover 100 may provide a physicalopening to access a display, a camera, a button, a control, otherinput/output (I/O) interfaces, etc. of the host mobile device 110. Insome embodiments, the mobile device cover 100 does not cover the maindisplay of the host mobile device 110 when the mobile device cover 110is attached to the host mobile device 110. In some embodiments, themobile device cover 100 may provide a transparent or partiallytransparent cover portion, for example, over a display or other portionsof the host mobile device 110. The transparent cover portion can be madeof materials that, for example, do not interfere with the operation ofany of the touch screens, speakers, and/or buttons of the host mobiledevice 110. In some embodiments, the materials can be substantiallytransparent to wireless communication links used by the host mobiledevice 110 and/or the mobile device cover 100. The transparent coverportion may also protect areas of the host mobile device 110 such astouch screens from scratches or other damage.

Some embodiments according to the present disclosure may provide thatthe mobile device cover 100 is made of one or more of the followingmaterials: silicone, rubber, metal, plastic, polymers, polycarbonate,composites, cloth, metal, wood, acrylic, glass, plexiglass, and/or othermaterials. The cover material may be, at least in part, opaque ortransparent. The cover material may assist a user in gripping the hostmobile device 110 and may protect the host mobile device 110. The covermaterial may be, for example, one or more of the following: shockresistant, shock proof, shatter proof, shatter resistant, dustresistant, dust proof, water resistant, water proof, etc. In someembodiments, the mobile device cover 100 may be made up of multiplepieces (e.g., portions 100 a, 100 b, 100 c, one or more printed circuitboards, housings, etc.), as shown in FIGS. 1B and 1C. In someembodiments, the multiple pieces of the mobile device cover 100interlock together to house, become the back panel of the host mobiledevice 110, and/or to connect (e.g., physically and/or electricallyconnect, snap, interlock, etc.) to the host mobile device 110.

Referring to FIGS. 1B and 1C, the mobile device cover 100 can include,for example, circuitry 150 and lights 160 disposed on one or moreprinted circuit boards. In some embodiments, the circuitry 150 caninclude one or more of the following: one or more processors, one ormore non-transitory memories, signal processors, light controlcircuitry, light drive circuitry, battery recharging circuitry, batterycontrol circuitry, display control circuitry, sensors, input interfacecircuitry, output interface circuitry, digital-to-analog converters,analog-to-digital converters, wired transceivers, wireless transceivers,input/output ports, input/output interfaces, and antennas. The one ormore non-transitory memories can be configured to store, for example,data (e.g., input data, data received from the host mobile device 110,stored reference data, stored configuration data, stored personal data,etc.) and processor-executable instructions or code for use with the oneor more processors. The circuitry 150 can be connected, for example, toand/or can include the lights 160. Some embodiments provide that thelights can include one or more of the following: LEDs, flexibleactive-matrix OLEDs (AMOLEDs), OLEDs, phosphor-based LEDs, white LEDs(WLEDs), multi-color WLEDs, semiconductor LEDs, other types of LEDs,LCDs, LCD touch screens, electroluminescence, pixel displays, etc., andcan be arranged or used in a specific pattern, array, sequence, etc.Some embodiments provide that the lights can be raised or provide bumpysurfaces suitable for use in a Braille system. Various components and/orelements of the circuitry 150 can be connected to each other through oneor more buses, for example.

The mobile device cover 100 can also include, for example, a battery 170(e.g., a rechargeable battery, a “watch” battery, etc.) that can be usedto power, for example, the circuitry 150, the lights 160, and any othercircuitry or components in the mobile device cover 100 and/or the hostmobile device 110. The battery 170 can also be used to power the hostmobile device 110 and/or to recharge a battery in the host mobile device110. In some embodiments, the mobile device cover 100 does not have abattery and instead can be powered by the host mobile device 110. Someembodiments according to the present disclosure provide that the battery170 can be rechargeable or not rechargeable. If not rechargeable, thebattery 170 can be replaced. Some embodiments of the battery 170include, for example, a lithium battery, an alkaline battery, asilver-oxide battery, nickel cadmium battery, nickel metal hydridebattery, lithium ion battery, lithium ion polymer battery, etc. Ifrechargeable, then the battery 170 can be recharged, for example, bydrawing energy from one or more interfaces of the host mobile device 110(e.g., an audio port, an earphone jack, a docking port (e.g., a USB-typeport, a lightning connector port, a power and signaling connection port,etc.), a wireless charging pad, etc.). The battery 170 can also berecharged by drawing energy separate from or independent of the hostmobile device 110. Similarly, a rechargeable battery of the host mobiledevice 110 can be charged through one or more interfaces of the hostmobile device 110 that are electrically or wirelessly connected to themobile device cover 100. The rechargeable battery of the host mobiledevice 110 can also be recharged by drawing energy separate from orindependent of the host mobile device 110.

For example, independent of whether the mobile device cover 100 isconnected to the host mobile device 110, the mobile device cover 100 canbe separately plugged into a wall outlet or wirelessly charged at awireless charging station. The mobile device cover 100 can also becharged by plugging it into a computer, a charger bank, a generator,etc. via a USB-type connection, for example. The battery 170 of themobile device cover 100 can be charged by a piezoelectric batterycharger, for example. In some embodiments, the piezoelectric batterycharger can convert force (e.g., caused by pressure, movements,mechanical forces, etc.) into electrical energy for use by the battery170. Some embodiments contemplate converting other types of energy(e.g., sound energy, light energy, electromagnetic energy, magneticenergy, thermal energy, moving air, wireless energy, etc.) intoelectrical energy to charge the battery 170. In some embodiments, themobile device cover 100 can utilize charging methods such as conductiveand inductive charging.

In some embodiments, the battery 170 of the mobile device cover 100 canalso be recharged when the host mobile device 110 is wirelessly orwiredly connected to a power source (e.g., AC and/or DC power source).For example, the battery 170 of the mobile device cover 100 can berecharged when the host mobile device 110 is connected to a wall outlet,for example, such as when a docking port of the host mobile device 110is connected to a wall outlet. The battery 170 may receive energydirectly from the wall outlet (e.g., via connecting the mobile devicecover 100 directly to the wall outlet) or indirectly from the walloutlet through the host mobile device 110. In addition, the battery 170may receive energy when a docking port or some other interface of thehost mobile device 110 is connected to a computer while electrically orwirelessly connected to the mobile device cover 100. Some embodimentsaccording to the present disclosure contemplate that the circuitry 150receives power from the host mobile device 110 without using the battery170 or in combination with the battery 170. Thus, some embodimentsaccording to the present disclosure might not have a dedicated batteryas part of the mobile device cover 100, or might use the battery 170 asa back-up power source.

In some embodiments, just as the battery 170 of the mobile device cover100 can draw on energy from the host mobile device 110, the battery ofthe host mobile device 110 can draw on energy from the mobile devicecover 100 to recharge the battery of the host mobile device 110 or tosupplement power to the host mobile device 110. For example, asrechargeable batteries age, they are less capable of fully powering themain processor on the host mobile device 110. The aging batteries havereduced full charge capacity and provide less power, voltage, and/orcurrent during normal operation. As a result, some processors (e.g.,central processor, graphics processor, general processor, dedicateprocessor, etc.) will enter a power-save mode in which processor speed(e.g., clock speed) and/or load capacity (e.g., peak load) are reducedto conserve power and/or energy which is detrimental to performanceand/or inconvenient to the user. In such a situation, the host mobiledevice 110 can supplement the power and capacity of its own battery withthe battery 170 of the mobile device cover 100, thereby avoiding thepower-save mode of the processor of the host mobile device 110 or viceversa. Accordingly, the processors in the host mobile device 110 cancontinue to operate at normal operation speeds and load capacities.Further, by supplementing power and capacity of the host mobile device100, the battery 170 of the mobile device cover and the battery of thehost mobile device 110 can be used to power a turbo mode in theprocessor of the host mobile device 110 or vice versa. For example, inturbo mode, the processor (e.g., a central processor, a graphicsprocessor, a general processor, a dedicated processor, etc.) of the hostmobile device 110 can operate at one or more of the following: a highervoltage, a higher current, a higher power, a higher load capacity,and/or a higher clock speed than during normal operation. During turbomode, the host mobile device 110 and/or the mobile device cover 100 canoperate with greater performance and can perform moreprocessor-intensive applications.

In some embodiments, when the host mobile device 110 is electricallyconnected to the mobile device cover 100 (e.g., when the host mobiledevice 110 has been inserted into the mobile device cover 110) and themobile device cover 100 is plugged into a wall outlet, for example, thebattery 170 of the mobile device cover 100 and the battery of the hostmobile device 110 charge at the same time. In some embodiments, thebattery of the host mobile device 110 charges without a decrease incharge speed even when the host mobile device 110 and the mobile devicecover 100 are charged at the same time via the electrical connection(e.g., via a port 147) of the mobile device cover 100 to the wall plug,for example.

FIG. 1D shows an exploded side perspective view of an exemplary mobiledevice cover 100 according to an embodiment of the present disclosure.In some embodiments, the circuitry 150 can be embedded in the mobiledevice cover 100. In some embodiments, the circuitry 150 may include,for example, one or more circuit boards 150 a including, for example,one or more of the following: one or more processors, circuit elementsor components, an integrated circuit, an integrated circuit chip, asystem on a chip, etc. The circuitry 150 may also include, for example,one or more sensors 150 b (e.g., an audio sensor, a signal sensor, anoptical sensor, a wireless signal sensor, a wireless receiver, awireless transceiver, an electrical sensor, a power sensor, a batterysensor, an electromagnetic sensor, a vibration sensor, gyroscope sensor,iris scanner, fingerprint sensor, accelerometer, proximity sensor,barometer, hear rate sensor, a biometric sensor, etc.). Components 150 aand 150 b can be part of the same circuit board or can be part ofseparate circuit boards, for example, that are connected to form, inpart, the mobile device cover 100. A sensor can be part of components150 a, 150 b, or both. In some embodiments, the mobile device cover 100can include multiple circuit boards or multiple-layered circuit boards.

FIG. 2 illustrates an exemplary circuit arrangement according to anembodiment of the present disclosure. Referring to FIG. 2, a simplifiedblock diagram is shown of the circuitry 150. The circuitry 150 mayinclude one or more of the following: a processor 200, a memory 210, anI/O device 220, a bus 230, driver circuitry 240, and lights 160. Theprocessor 200, the memory 210, the I/O device 220, the driver circuitry240, and the lights 160 can be coupled to each other via one or morebuses 230. The circuitry 150 can include more or less than one processor200, one memory 210, one I/O device 220, one bus 230, one driver circuit240, and two lights 160 as illustrated in FIG. 2. Thus, some embodimentscontemplate employing different numbers of various elements of thecircuitry 150.

The driver circuitry 240 can include, for example, one or more of thefollowing: light drivers, LED drivers, shift registers, constant currentsupply, constant voltage supply, switching supply, FET amplifier, BJTamplifier, etc. In addition, some embodiments according to the presentdisclosure contemplate using a plurality of sensors, processors,memories, and/or driver circuits. Some embodiments provide that thedriver circuitry 240 can be part of the processor 200 and, in someembodiments, can take the place of the processor 200. Some embodimentsprovide that the driver circuitry 240 and other circuitry can beincorporated into a system on a chip (SOC). In some embodiments, thedriver circuitry 240 can be configured to control any amount orarrangement of similar or different lights 160, including a full display(e.g., a touch-sensitive screen, LED screen, etc.). In some embodiments,the driver circuitry 240 can be configured to power any number orarrangement of similar or different lights 160.

The I/O device 220 can include, for example, one or more of thefollowing: an input device (e.g., a button), a touch-screen display, awired and/or wireless transceiver (e.g., cellular transceiver, Bluetoothtransceiver, WLAN transceiver, etc.), a wired and/or wirelesstransmitter, a wired and/or wireless receiver, an antenna, a speaker, amicrophone, an I/O port (e.g., earbud port, earphone port, microphoneport, speaker port, etc.), an I/O interface, data connector port, powerconnector port, wired and/or wireless communication device, GPSreceiver, a network interface, etc.

The processor 200 can include, for example, one or more of thefollowing: a general processor, a central processing unit, a digitalfilter, a microprocessor, a digital processor, a digital signalprocessor, a microcontroller, a programmable array logic device, acomplex programmable logic device, a field-programmable gate array andan application specific integrated circuit (ASIC), and a memory (e.g., acache). Code, instructions, software, firmware, and data including, forexample, a mobile application may be processed and/or executed by theprocessor 200 to perform any of the operations, functions, and/orfeatures described in the present disclosure. Further, the code,instructions, software, firmware, and/or data including, for example,the mobile application may be stored in the processor 200 and/or thememory 210. The code, instructions, software, firmware, and/or data canbe automatically or manually updated, upgraded, modified, replaced,overwritten, supplemented, etc. via a wireless or wired connection.

The memory 210 can include, for example, one or more of the following: anon-transitory memory, a non-transitory processor readable medium, anon-transitory computer readable medium, a read only memory (ROM), arandom access memory (RAM), DRAM, EPROM, EEPROM, F-RAM, FIFO, NVRAM,SRAM, a cache, a semiconductor memory, a magnetic memory, an opticalmemory, a flash memory, a flash card, a compact flash card, memorycards, secure digital memory cards, a microcard, a minicard, anexpansion card, a smart card, a memory stick, a multimedia card, apicture card, flash storage, a subscriber identity module (SIM) card, ahard drive (HDD), a solid state drive (SSD), etc. The memory 210 may beconfigured to store code, instructions, software, firmware, and data foruse by the processor 200 and may be external, internal, or both withrespect to the processor 200. In some embodiments, the memory 210 alsostores a mobile application, settings, parameters, values, lightshows,icons (e.g., icons, emojis, graphical elements, etc.), animations,scrolling text, etc. Further, the code, instructions, software,firmware, and/or data can be automatically or manually updated,upgraded, modified, replaced, overwritten, supplemented, etc. via awireless or wired connection.

Some embodiments provide that a mobile application can be downloadedonto the host mobile device 110 to provide a graphical user interfacethat can be used, for example, to control the mobile device cover 100.The mobile application can run on the host mobile device 110 and/or themobile device cover 100. The graphical user interface can be on the hostmobile device 110 and/or the mobile device cover 100. Further, themobile application can be automatically or manually updated, upgraded,modified, replaced, overwritten, supplemented, etc. via a wireless orwired connection.

FIGS. 3 and 4 show an exemplary launch screen page 300 and an exemplaryfront page 400 according to an embodiment of the present disclosure. Themobile application can be represented as an icon (e.g., a graphicalelement of a graphical user interface) on the display (e.g., screen) ofthe host mobile device 110 and/or the mobile device cover 100. When theicon is selected, the mobile application runs on the host mobile device110 (and/or the mobile device cover 100) and a launch page 300 as shownin FIG. 3 is displayed by the host mobile device 110 (and/or the mobiledevice cover 100). Subsequently, a front page 400 as shown in FIG. 4 isdisplayed. While the front page 400 is being displayed, the mobileapplication attempts to wirelessly and/or wiredly connect the hostmobile device 110 and the mobile device cover 100 according to anembodiment of the present disclosure. In one embodiment, the mobileapplication attempts to wirelessly pair the mobile device cover 100 andthe host mobile device 110, which are both Bluetooth-enabled. If themobile application is not successful in making a connection (e.g., aconnection between previously paired devices 100, 110), then aconnection page 500 is opened as shown in FIG. 5, or an alternativeconnection method can be established via, for example, a USB-typeconnection, WiFi connection, Bluetooth connection, Zigbee connection,etc. If a successful connection is made, then an exemplary home page 700is opened as shown in FIG. 7. If the connection is lost, then the mobileapplication opens the front page 400 or the connection page 500.

By selecting the pair icon 410 (e.g., graphical button) shown in FIG. 4,an exemplary connection page 500 according to an embodiment of thepresent disclosure as shown in FIG. 5 is opened that allows forconfiguring wireless and/or network connections. The connection page 500enables the user to select a device for pairing (e.g., a mobile devicecover 100) and/or a network for connection. The list 520 of devices canbe refreshed by a user gesture such as a swipe, for example, otherwise,the list is refreshed periodically. In some embodiments, selecting aparticular device such as a mobile device cover 100, for example,initiates a verification process such as a pin verification process, forexample. After a prompt from the mobile application, entry of thecorrect pin (e.g., supplied by the mobile device cover 100) within aparticular time limit or by a particular number of attempts causes themobile application to open the home page 700 shown in FIG. 7.Configuring of the mobile application and/or the mobile device cover 100can occur based on a selection or an input of a particular model numberor particular type of mobile device cover 100. Incorrect entry of thepin number within the particular time limit or after a particular numberof failed attempts causes the mobile application to open the front page400 or the connection page 500. By selecting a back icon 510, forexample, the mobile application navigates to the front page 400, theconnection page 500, or a previous page.

By selecting the information icon 420 (e.g., an “i” icon) in FIG. 4, anexemplary instructions page 600 according to an embodiment of thepresent disclosure as shown in FIG. 6 is opened which providesdescriptions and helpful information about various items beingdisplayed, for example, on a push button or element selectable menu. Bytapping or toggling the back icon 610 (e.g., back graphical button), forexample, by making a gesture on the screen (e.g., swiping left to righton the screen), or by moving the mobile device cover 100 and/or hostmobile device 110 in a particular way, the home page 700 as shown inFIG. 7 or a previous page can be opened.

FIG. 7 shows an exemplary home page 700 according to an embodiment ofthe present disclosure. In some embodiments, upon successful connectionand pairing, the mobile application displays a home page 700 as shown inFIG. 7. The home page 700 provides a graphical user interface by whichthe user can further navigate the mobile application. Referring to FIG.7, the home page 700 includes icons or hyperlinks to open, for example,a phone page, a messages page, an email page, anotifications-for-applications page, a lighting-for-contacts page, abattery page, a lighting page, a back design page, and a settings page.In addition, the home page 700 provides for controlling a brightness(e.g., via a brightness slider 710) of a display and/or a volume for aspeaker for the mobile device cover 100 and/or the host mobile device110. In some embodiments, the home page 700 provides an icon 720 (e.g.,a graphical element) that can be toggled on or off as to whether todisplay incoming notifications on the mobile device cover 100, forexample.

In some embodiments, the mobile application enables the user with theability to set up a particular lightshow, a particular icon (e.g., anicon, an emoji, a custom-designed graphical element), and/or aparticular text (e.g., scrolling text) to be displayed for a particulartype of communication (e.g., phone, message, email. etc.), a particularcontact, and/or a particular type of communication (e.g., phone,message, email, etc.) for that particular contact on a contact liststored in the host mobile device 110 and/or the mobile device cover 100.The mobile application also enables the user to customize the selectedlightshow, icon, text, etc.

By selecting the phone icon 730 on the home page 700, a phone page 800according to an embodiment of the present disclosure is opened as shownin FIG. 8. In some embodiments, a messages page and an email page areopened by selecting the message icon 735 and the email icon 745,respectively, of the home page 700 and operate in a similar manner asthe phone page 800. In some embodiments, after the phone icon 730 isselected, a lightshows page 810 (e.g., for phone notifications) is firstshown for the phone page 800 as in FIG. 8; however, other selectableoptions including an icons page and a scrolling text page can also beopened by selecting the corresponding icons 820, 830 (e.g., graphicalbuttons or tabs). Referring to FIG. 8, the lightshows page 810 providesone or more graphical elements on a graphical user interface that enablethe user to select a particular lightshow (e.g., flare) from a list oflightshows that can be assigned, for example, to a particular contact.Parameters for the lightshows are also selected. For example, a speedand a duration are set (e.g., via graphical sliders 840, 850 as shown inFIG. 8) for the selected lightshow, which includes animation, forexample. Other adjustable or selectable parameters can include lightintensity, colors, size, pulsing, bursting, etc. The selected lightshowwith any selected particular lightshow parameters is assigned to aparticular contact (e.g., phone contact, phone number, etc.), and thisinformation is sent to the mobile device cover 100, for example. Theassignments are stored in the mobile device cover 100, the host mobiledevice 110, and/or the mobile application. The lightshows page 810provides an icon 860 (e.g., a preview-on-case icon) that, when selected,causes the mobile device cover 100 to demonstrate the currently selectedlightshow according to the selected lightshow parameters on the LEDs (orother lights or lighting devices) and/or on one or more screens of themobile device cover 100. In some embodiments, the lightshows page 810can provide an icon (e.g., a preview-in-the-mobile application icon) orcan automatically display in a portion 870 of the lightshows page 810 orin a separate page of the mobile application, a preview of the selectedlightshow according to the set lightshow parameters. For example, themobile application can provide a separate preview page or previewsection 870 as shown in FIG. 8 of the lightshows page 810 that shows theselected lightshow according to the selected settings (e.g., with anyselected animation at a particular speed for a particular duration) onan image of the mobile device cover 100 according to the selected modeland/or other characteristics (e.g., a blue back design or color). Thepreview in the mobile application can provide the user with a preview ofthe selected lightshow and lightshow options (e.g., on the host mobiledevice 110) without necessarily demonstrating the lightshow on the LEDsand/or screen of the mobile device cover 100. However, the preview inthe mobile application (e.g., on the host mobile device 110) can also beplayed concurrently with or separately from a preview on the case (e.g.,a preview using the LEDs and/or screen of the mobile device cover 100).In some embodiments, the lightshows page 810 provides an icon that, whenselected, enables a user to download or purchase (e.g., as part of anin-application purchases page) additional lightshows or features. Insome embodiments, clicking on a share icon enables the user to share theparticular lightshow, icon, and/or scrolling text with others (e.g.,friends, selected individuals, contacts, etc.). The sharing can befacilitated via a wired and/or wireless communication or transfer, atext, an email, a social media post or communication, etc. as text, afile, a graphics interchange format (GIF) file, an image, a video, apicture, a file stored in camera roll, etc. Selecting the back button880 (or other actions such as backwards swipes) brings back the homepage 700 or a previous page. Selecting (e.g., tapping or some other userinput) on the assigned contacts button or link 890 causes an assignedcontacts page 900 to open as shown in FIG. 9.

FIG. 9 shows an exemplary assigned contacts page 900 according to anembodiment of the present disclosure. The assigned contacts page 900enables the user to view and select a particular lightshow (e.g., lightpattern, lightshow, animation, etc.) for assignment (e.g., assignment orre-assignment). In some embodiments, a lightshow includes a series ofimages that are displayed on the mobile device cover 100 and/or themobile application. The assigned contacts page 900 also enables the userto view the currently assigned lightshow for a particular notificationcategory (e.g., email, message, phone, etc.). Further, the assignedcontacts page 900 can also identify duplicate lightshow assignments.Colors or other indicators enable the user to easily see duplicateassignments. Referring to FIG. 9, the Halo lightshow, which is shown asa red button 910, is assigned both to contacts Adam Fee and Abc Xyz. Theparticular colors used are merely exemplary. The Star lightshow, whichis shown as a blue button 920, is uniquely assigned to Amanda Bee. Theemail icon, the message icon, the phone icon, and the Happy icon, whichare shown as green buttons 930, indicate uniquely assigned icons foremails generally, messages, phone calls generally, and Ally Arm.Selecting the back button 940 (or other actions such as backwardsswipes) brings back a previous page (e.g., the lightshows page 810).

Selecting the icons button 820 (e.g., graphical tab) at the top of thephone page 800 shown in FIG. 8 opens an exemplary icons page 1000according to an embodiment of the present disclosure as shown in FIG.10. The icons page 800 of the mobile application enables the user toselect a particular icon, icon parameters, and/or animation forassignment (e.g., assignment or re-assignment). Selecting a particularicon such as, for example, the phone icon 1010 as shown in FIG. 10,causes the mobile application to display the phone icon as it would lookwhen displayed on the mobile device cover 100 on a portion 1020 of thepage 1000 or on a separate page. Information relating to the selectionof the phone icon 1010 including any icon parameters and assignments issent to the mobile device cover 100. By selecting the animations button1030, different types of animations are listed for application to thephone icon, for example. In some embodiments, the list includes onlythose animations that are applicable for the selected icon. In someembodiments, the animations can include moving across the screen,pulsating, bursting, dynamically changing colors, rotating, dynamicallychanging in size, etc. Selecting an icon parameter such as, for example,an animation, causes the mobile application to display the selected iconon a portion 1020 of the display according to the selected animationsand/or icon parameters, and to send the icon-related information to themobile device cover 100. Icon parameters such as a speed and a durationare set (e.g., via graphical sliders 1040, 1050 as shown in FIG. 10) forthe selected icon and the applied animation. In some embodiments, theicons page 1000 provides an icon 1060 (e.g., a preview-on-case icon)that, when selected, causes the mobile device cover 100 to demonstratethe currently selected icon according to the selected parameters and/oranimations on the mobile device cover 100 as shown in FIG. 25C, forexample. For example, the lights 160 (e.g., LEDs, screens, etc.) of themobile device cover 100 light up according to the selected icon,animations, and/or parameters to preview the response of the mobiledevice cover 100 for the particular assignment (e.g., a particularcontact, type of communication, type of notification, alert, etc.). Insome embodiments, the icons page 1000 can provide an icon (e.g., apreview-in-the-mobile application icon) or can automatically display ina portion 1020 of the icons page 1000 as in FIG. 10 or 25A, or in aseparate page 2500 of the mobile application as in FIG. 25B, a previewof the selected lightshow according to the set lightshow parameters. Thepreview changes as the user makes changes. The mobile application canalso provide a separate preview page 2500 as shown in FIG. 25B orpreview section 1020 as shown in FIG. 10 (or FIG. 25A) of the icons page1000 that shows the selected icon according to the selected settings(e.g., with any selected animation at a particular speed for aparticular duration) on an image of the mobile device cover 100according to the selected model and/or other characteristics (e.g., ablue back design or color). The preview in the mobile application canprovide the user with a preview of the selected icon and icon options(e.g., on the host mobile device 110) without necessarily demonstratingthe icon on the LEDs and/or screen of the mobile device cover 100.However, the preview in the mobile application (e.g., on the host mobiledevice 110) can also be played concurrently with a preview on the case(e.g., a preview using the LEDs and/or screen of the mobile device cover100) as shown in FIG. 25C. In some embodiments, clicking on a share iconenables the user to share the particular lightshow, icon, and/orscrolling text with others (e.g., friends, selected individuals,contacts, etc.). The sharing can be facilitated via a wired and/orwireless communication or transfer, a text, an email, a social mediapost or communication, etc. as text, a file, a graphics interchangeformat (GIF) file, an image, a video, a picture, a file stored in cameraroll, etc. Selecting the back button 880 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, the icons page 1000 provides an icon that, whenselected, enables a user to download or purchase (e.g., as part of anin-application purchases page) additional icons or features. Selectingthe back button 1070 (or other actions such as backwards swipes) bringsback the home page 700 or a previous page.

Selecting the scrolling text button 830 (e.g., graphical tab, graphicalelement, etc.) at the top of the phone page 800 shown in FIG. 8 or thescrolling text button 1080 at the top the icons page 1000 shown in FIG.10 opens an exemplary scrolling text page 1100 according to anembodiment of the present disclosure as shown in FIG. 11A. The scrollingtext page 1100 enables the user to select a text and/or a scrolling textand/or scrolling text parameters for assignment (e.g., assignment orre-assignment). Selecting text, scrolling text, and/or scrolling textparameters causes the mobile application to send the selected text,scrolling text, and/or scrolling text parameters to the mobile devicecover 100. Referring to FIG. 11B, an exemplary scrolling text page 1105is shown with a preview pane 1115 that enables the viewing of thescrolling text (e.g., customized scrolling text, preset scrolling text,etc.). The speed and text can be changed using the scrolling text page1105. Further, as will be explained below with respect to FIGS. 25D-E,for example, the font and the orientation of the scrolling text can bechanged and previewed. The preview changes as the user makes changes tothe scrolling text. The preview pane 1115 can also be a pop-up window ora separate page. The previewed pane 1115 can also illustrate variouschanges in the scrolling text on a representation of a selected model ofthe mobile device cover 100. Further, the previewed display can also beactually displayed on the mobile device cover 100 to view the display(e.g., scrolling text display) in view of any scrolling text changes,for example. In some embodiments, clicking on a share icon 1125 enablesthe user to share the scrolling text (and/or particular lightshow, icon,etc.,) with others (e.g., friends, selected individuals, contacts,etc.). The sharing can be facilitated via a wired and/or wirelesscommunication or transfer, a text, an email, a social media post orcommunication, etc. as text, a file, a graphics interchange format (GIF)file, an image, a video, a picture, a file stored in camera roll, etc.

By selecting an icon 1110 (e.g., a plus icon), an exemplary add itempage 1200 according to an embodiment of the present disclosure is openedas shown in FIG. 12. The add item page enables a user to select textoptions for scrolling on the mobile device cover 100. Referring to FIG.12, a user can add words, symbols, names, a phone type, and/or a phonecharacter for scrolling. A user can cause the word “Call” to scrollacross the mobile device cover 100 as part of a phone call notificationor as part of a calendar alert, for example. In addition, differentoptions for scrolling the name of the caller are available such as thefull name, first name, first name and remaining name in initials, allinitials, etc. Furthermore, the user can add a phone type, a phonecharacter, or some other customized graphics for scrolling across themobile device cover 100 as part of a notification, for example.Selecting the back button 1210 (or other actions such as backwardsswipes) brings back the scrolling text page 1100.

Referring back to FIG. 11, further options for scrolling includechanging the order and appearance of words, names, phone type, phonecharacter, and/or icon for scrolling. The order of these options can bechanged, for example, by moving the particular category of informationbeing scrolled into a different position in the display order 1120 byselecting and moving the three lined icon 1130. The scrolling text page1100 enables, via one or more graphical elements 1140, a user to displaythe icon before or after the scrolling text, or not at all. Thescrolling text page 1100 further enables the user to select a type ofseparator, via a selection menu 1150, between different categories(e.g., name, phone character, phone type, etc.) for scrolling. Forexample, the separator can be one or more lines or spaces betweendifferent categories (e.g., phone character, name, phone type, icon,etc.). In addition, the scrolling text page 1100 provides for the userto determine, via selection menus 1160, 1170, the number of displayrepetitions (e.g., one, two, three, etc.) of the scrolling message and ascroll speed. In some embodiments, the scrolling text page 1100 providesan icon 1180 (e.g., a preview-on-case icon) that, when selected, causesthe mobile device cover 100 to demonstrate the currently selectedscrolling text and/or icon according to the selected scrolling textparameters and/or animations on the mobile device cover 100. In someembodiments, the mobile application can preview the scrolling text onthe host mobile device 110, for example, as part of the lightshows page810, the icons page 1000, the scrolling text page 1100, or a separatepage, the selected scrolling text with or without accompanying icons orlightshows according to the scrolling text parameters and/or otherparameters as it would appear on the mobile device cover 100. Forexample, the mobile application can provide a preview page that includesan image of the mobile device cover 100 (e.g., the selected modelincluding color and other characteristics of that model of the mobiledevice cover 100) with the scrolling text as it would appear on themobile device cover 100 during a notification or other display, forexample. Selecting the back button 1190 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, by selecting a notifications-for-applicationsbutton or link 740 (e.g., graphical element in a graphical userinterface, the text “Notifications for App,” etc.) on the home page 700as shown in FIG. 7, an exemplary notifications-for-applications page1300 is opened as shown in FIG. 13. The notifications-for-applicationspage 1300 enables users to view and change settings for applications forwhich the mobile application and the mobile device cover 100 supportcustom notifications. Referring to FIG. 13, a list of applications 1310is shown for which the mobile application and the mobile device cover100 support notifications. Some embodiments provide that the list ofmobile applications include the mobile application installed on the hostmobile device 110, any of the user's other host mobile devices or mobiledevices, the mobile device cover 100, etc. For each listed application,the user can select (e.g., tap, toggle, etc.) various options. In someembodiments, a button or icon (e.g., a graphical element of a graphicaluser interface) is provided to turn on or off a particular notificationparameter. Referring to FIG. 13, for each listed application, agraphical button 1320 is provided to turn on or off the displaying ofnotifications from the calendar application on the mobile device cover100, for example. A graphical button 1330 is also provided for eachlisted application to turn on or off the displaying of the respectiveapplication name (e.g., Amazon, Calendar, etc.) on the mobile devicecover 100 when the mobile application receives a notification for therespective application. A graphical button 1340 is provided for eachlisted application to turn on or off the displaying of a particular icon(e.g., application icon, customized icon, emoji, etc.) corresponding tothe respective application when the mobile application receives anotification for the respective application. In addition, a graphicbutton 1350 is provided for each listed application to turn on or offthe displaying of the contents of a notification (e.g., scrolling thecontents of a notification on the mobile device cover 100, text or mediafrom an email, a message, a textual alert, a sound, a transcription of avoicemail, etc.) when the mobile application receives the notificationfor the respective application. The notifications-for-applications pagealso provides a search bar 1360 for searching for applications by name,for example. Selecting the back button 1370 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, by selecting a lighting-for-contacts button or link750 (e.g., graphical element in a graphical user interface, the text“Lighting for Contacts,” etc.) on the home page 700 as shown in FIG. 7,an exemplary lighting-for-contacts page 1400 is opened as shown in FIG.14. The lighting-for-contacts page 1400 enables users to view and assignlightshows, icons, scrolling text, etc. for display on the mobile devicecover 100, for example. Referring to FIG. 14, by selecting (e.g.,tapping or some other user input) a contact name 1410 or a graphicalbutton 1420 indicating an assigned lightshow, icon, etc., alightshows-for-contacts page 1500 or an icon-for-contacts page 1600 isopened as shown in FIG. 15 or 16, respectively. In some embodiments,swiping left to right or right to left on the contact name 1410 or thegraphical button 1420 indicating an assigned lightshow or icon, forexample, causes the removal of the particular contact and/or thelightshow or icon assignment for a particular contact. The screenincluding the data displayed on the screen can be refreshedcontinuously, periodically, or aperiodically by a gesture (e.g., a swipeup or down, selecting a graphical element, etc.) on the screen.Selecting the back button 1430 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 15 shows an exemplary lightshows-for-contacts page 1500 accordingto an embodiment of the present disclosure. In particular, by selectingthe contact name, e.g., Hank Williams, or a graphical button indicatinga lightshow assigned to Hank Williams on the lighting-for-contacts page1400, the exemplary lightshows-for-Hank-Williams page 1510 opens asshown in FIG. 15. The lightshows-for-contacts page 1500 enables a userto change the lightshow and lightshow parameters assigned to aparticular contact. The current lightshow for Hank Williams is listed asthe Star lightshow 1520; however, other lightshows can be selected(e.g., by tapping or toggling on the lightshow name such as “Nova”) fromthe lightshows list 1530 for assignment to Hank Williams. Parameters forthe selected lightshow such as a speed (e.g., speed of an animation ofthe lightshow) and a duration of the lightshow care are controlled bysliding controls 1540, 1550 (e.g., graphical sliders). Data relating tothe selected lightshow and lightshow parameters is sent to the mobiledevice cover 100. The selected lightshow is shown or previewed on aportion 1560 of the lighting-for-contacts page 1500 including anyselected animations in accordance with any selected lightshowparameters. The preview also reflects the selected model including coloror other characteristics (e.g., arrangement of LEDs or screens,resolution, etc.) of the selected model of the mobile device cover 100so that the user can see how the lightshow looks on the selected modelof the mobile device cover 100. The lightshows-for-contacts page 1500also provides an icon 1570 (e.g., a preview-on-case icon) that, whenselected, causes the mobile device cover 100 to demonstrate (e.g.,actually display on the mobile device cover 100, cause LEDs of themobile device cover 100 to light according to the lightshow, animations,and parameters, cause screens of the mobile device cover 100 to displayaccording to the lightshow, animations, and parameters, etc.) thecurrently selected lightshow including any selected animations accordingto any selected lightshow parameters. Selecting (e.g., tapping or someother user input) on the assigned contacts button or link 1580 causesthe assigned contacts page 900 to open. In some embodiments, thelightshows-for-contact page 1500 provides an icon that, when selected,enables a user to download or purchase (e.g., as part of anin-application purchases page) additional lightshows or features.Selecting the back button 1590 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 16 shows an exemplary icons-for-contacts page 1600 according to anembodiment of the present disclosure. In particular, by selecting thecontact name, e.g., Hank Williams, or a graphical button indicating anicon assigned to Hank Williams on the lighting-for-contacts page 1400,the icons-for-Hank-Williams page 1610 opens as shown in FIG. 16.Alternatively, if the lightshows-for-Hank-Williams page 1510 is alreadyopened as shown in FIG. 15, then selecting the icons button 1595 (e.g.,graphical tab) also opens the icons-for-Hank-Williams page 1610. Theicons-for-contacts page 1600 enables a user to change the icon (e.g., anicon, an emoji, a graphical element, a custom-designed graphicalelement, a downloaded graphical element, a stored graphical element,etc.) and icon parameters assigned to a particular contact and/or for aparticular type of notification for the particular contact. For example,in addition to speed and duration parameters, the icons-for-contactspage 1600 can also add animation to the icon. Other parameters that canbe changed include, for example, parameters that change the color, size,intensity, pulsating, bursting, etc. of the icon. The informationindicating the selected icon and icon parameters is sent to the mobiledevice cover 100. The selected icon is shown or previewed on a portion1620 of the icons-for-contacts page 1600 (or on a separate page)including any selected animations in accordance with any selected iconparameters. The preview also reflects the selected model including coloror other characteristics (e.g., arrangement of LEDs or screens,resolution, etc.) of the selected model of the mobile device cover 100so that the user can see how the displayed icon looks on the selectedmodel of the mobile device cover 100. The icons-for-contacts page 1600also provides an icon 1630 (e.g., a preview-on-case icon) that, whenselected, causes the mobile device cover 100 to demonstrate (e.g.,actually display on the mobile device cover 100, cause LEDs of themobile device cover 100 to light according to the icon, animations, andparameters, cause screens of the mobile device cover 100 to displayaccording to the icon, animations, and parameters, etc.) the currentlyselected icon with any selected animations according to any selectedicon parameters. Selecting (e.g., tapping or some other user input) onthe assigned contacts button or link 1640 causes the assigned contactspage 900 to open. In some embodiments, the lightshows-for-contact pageprovides an icon that, when selected, enables a user to download orpurchase (e.g., as part of an in-application purchases page) additionalicons or features. Selecting the back button (or other actions such asbackwards swipes) brings back the home page 700 or a previous page(e.g., the lightshows-for-contacts page).

FIG. 17 shows an exemplary battery page 1700 according to an embodimentof the present disclosure that is opened, for example, when the batteryicon or link 760 on the home page 700 is selected. The battery page 1700enables a user to view and change the battery settings of mobile devicecover 100 and/or the host mobile device 110. For example, the batterypage 1700 enables a user to turn on an autocharging feature of themobile application. The user can set a start automatic chargingparameter and a stop automatic charging parameter. The parameters canbe, for example, battery charge percentages of the mobile device cover100 battery or the host mobile device 110 battery. In an exemplaryembodiment, a full battery charge is 100% and an exhausted batterycharge is 0%, for example. In addition to battery charge percentages,the parameters can be in units of energy, charge, power, capacity, etc.Each parameter is set by selecting (e.g., tapping, toggling, or someother user input) the increase (“+”) or decrease (“−”) graphical buttons1710 which incrementally increases or decreases the respective parameteraccordingly. In some embodiments, when the mobile application sensesthat the battery charge percentage of the host mobile device 110 batteryhas dropped to or below the start automatic charging parameter, then themobile application causes the mobile device cover 100 battery to chargethe host mobile device 100 battery until the stop automatic chargingparameter is reached. In some embodiments, similar automatic chargingparameters are used by the mobile application to also cause the hostmobile device 110 battery to charge the mobile device cover 100 battery.The parameters and information relating to whether the automaticcharging feature enabled is sent by the mobile application to the mobiledevice cover 100 and/or the host mobile device 110. By selecting themanual tab 1770, the battery page 1700 also enables to user to initiatemanual battery charging by selecting one battery (e.g., the mobiledevice cover 100 battery) to charge another battery (e.g., the hostmobile device 110 battery) according to a selectable condition (e.g.,battery charge, duration, etc.). The battery page 1700 also displays thebattery charge or battery charge percentages 1720, 1730 of the batteriesof the mobile device cover 100 and the host mobile device 110,respectively. When either battery is being charged, a charging icon 1740is displayed over the battery FIG. 1750 or over the portion 1760 of thebattery FIG. 1750 representing the battery that is being charged.Selecting the back button 1780 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 18 shows an exemplary lighting page 1800 according to an embodimentof the present disclosure that is opened, for example, when the lightingicon or link 770 on the home page 700 is selected. The lighting page1800 enables a user to set lighting settings for the mobile applicationand the mobile device cover 100. The lighting page lists a number oflighting options 1810 (e.g., flashlight, softlight, reading light,strobe light, panic light, etc.), the order of which can be changed bydragging the respective three lines icon 1820 corresponding to thelighting option to the appropriate place in the list. By selecting oneof the lighting options (e.g., flashlight, softlight, panic light,etc.), the respective light parameters 1830 (e.g., brightness via slider1840, duration via incremental adjustment buttons 1850, 1855, etc.) ofthe selected lighting option is viewed and can be modified. The mobiledevice cover 100 and/or the mobile application can operate according toone or more light options for a select time and/or duration, the one ormore light options provided by the mobile device cover 100 including: aflashlight; a soft light; a panic light (e.g., a bright bursting lightthat may accompany a piercing sound); a selfie light (e.g., a soft ringof light to naturally illuminate a face during a selfie and used inconjunction, for example, with a camera of the host mobile device 110 oran external camera); a reading light (e.g., an adjustable light forreading); a strobe light; icons (e.g., static or animated iconsincluding emojis displayed by one or more LEDs or on one or morescreens); light shows; light patterns; scrolling text (e.g., favoriteproverb or saying); and a clock. By selecting a respective icon (e.g.,an “i” icon 1860), a corresponding page (e.g., clock page, lightshowspage, icons page, etc.) opens. Referring to FIG. 18, when the flashlightoption is selected, the mobile device cover 100 operates as a flashlightby one or both of turning on selected LEDs or turning on one or morescreens to a particular brightness and/or hue, for example. The “on” and“off” tabs 1870, 1875 (e.g., icons, graphical elements, etc.) turn theflashlight on or off, respectively. The brightness and duration of theflashlight option can be set by a graphical slider 1840 or incrementaladjustment icons (e.g., “+” icon 1850 and “−” icon 1855). The variousoptions of the lighting page 1800 can be previewed in the mobileapplication (e.g., a portion of the lighting page 1800 or a separatepage) and/or on the mobile device cover 100 (and host mobile device110). As with all features described in the present disclosure, themobile device cover 100 operates whether physically connected to hostmobile device 110 or physically separated from the host mobile device110. Selecting the back button 1880 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

In some embodiments, the lighting page 1800 provides the setup of apanic light. panic alert, hazards, blinkers, etc. For example, for usein an emergency situation, a user can enable the lighting page to set upa panic alert. The panic alert can be activated by a graphical button onthe lighting page 1800 or on a home screen of the host mobile device110, or a physical button on the host mobile device 110. The panic alertcan also be activated by a graphical button on a screen or a physicalbutton on the mobile device cover 100. The panic alert can include, forexample, a panic light that is a light pattern at the highestintensities in a pattern (e.g., bursting light pattern, full LED on/offblue or other light pattern) configured to draw the most attention tothe user and/or to disorient an attacker of the user, for example.Further, the panic alert can be accompanied with a loud sound or voicethat is broadcast over the speakers of the mobile device cover 100and/or the host mobile device 110. The sound or voice is configured todraw the most attention to the user and/or to disorient an attacker ofthe user, for example. The panic alert can also include, with or withouta prompt, the dialing of an emergency phone number (e.g., policedepartment, security system, emergency contact, etc.) and otherconfigurations such as turning on the speaker phone. Other options ofthe panic alert can include, for example, the sending of text messagesto various contacts notifying the various contacts of the emergencysituation. The messages and/or phone call can include locationinformation (e.g., via a satellite-based location determining systemsuch as GPS and/or a ground-based location determining system) or otherdata to direct responders to the user location. The camera on the hostmobile device 110 can be activated during a panic alert to take picturesat selected intervals and/or to take one or more movies, which can besent automatically and/or stored. These options can be set up for thepanic light link on the lighting page 1800 that can open up a menu or aseparate page for these panic alert settings and/or parameters.

FIG. 19 shows an exemplary clock page 1900 according to an embodiment ofthe present disclosure that is opened, for example, when the clock iconor link 1885 (e.g., the “Clock” link) on the lighting page 1800 isselected. The clock page 1900 enables a user to set clock settings fordisplay by the mobile device cover 100. Referring to FIG. 19, differentclock faces 1910 can be selected, for example, by swiping the clock facemenu options (e.g., vertical view, horizontal view, portrait view,landscape view, stop watch view, etc.). Different parameters 1920 can beset by corresponding icons (e.g., graphical toggle switches 1930). Forexample, the following parameters can be set to affect the clock displayon the mobile device cover 100: 12-hour time format, 24-hour timeformat, displaying leading zeroes, blinking colon, etc. Further, customfields can be selected and/or set. For example, custom fields can beused to further display and/or set calendar information, time zoneinformation, additional time zone information times, highlighted worldtime zone map, etc. In some embodiments, the clock page provides an icon1940 (e.g., a preview-on-case icon) that, when selected, causes themobile device cover 100 to demonstrate the currently selected clockaccording to the selected clock face and other clock parameters on themobile device cover 100. Selecting the back button 1950 (or otheractions such as backwards swipes) brings back the home page 700 or aprevious page (e.g., the lighting page 1800).

FIG. 20 shows an exemplary back design page 2000 according to anembodiment of the present disclosure that is opened, for example, whenthe back design icon or link 780 (e.g., icon and/or “Lighting” link) onthe home page 700 is selected. The back design page 2000 enables a userto select a particular back design and/or mobile device cover 100 model.Referring to FIG. 20, a listing 2010 of back designs can be viewed byswiping up or down, for example, on a touch-sensitive screen of the hostmobile device 110. Selection of a particular back design occurs byselecting (e.g., tapping, toggling, or some other user input) theparticular back design graphic 2020 or the back design description 2030(e.g., the “Blue” link). The selection of the particular back designand/or mobile device cover 100 model affects the available lightshows,icons, animations, etc. that are adjustable for the selected back designand/or mobile device cover 100 model. For example, each mobile devicecover 100 model and/or particular back design can have its ownarrangement of lights (e.g., LEDs, indicators, etc.), screens, and/orfeatures. Accordingly, the available lightshows, icons, animations, etc.available for display on the light arrangements and/or screens of theselected mobile device cover 100 model and/or back design vary accordingto the selected mobile device cover 100 model and/or back design.Further, the mobile application uses the selected mobile device cover100 model and/back design when displaying selected lightshows, icons,animations, etc. during a preview, for example. For example, when themobile application is running on the host mobile device 110, the hostmobile device 110 can preview the selected lightshow, icons, animations,etc. using a page (e.g., lightshows page, lightshows-for-contacts page,icons page, a preview page, etc.) of the mobile application. Thegraphical preview provided by a page of the mobile applicationincorporates the selected mobile device cover 100 model and/or backdesign (e.g., structural features, colors, etc.). Selecting the backbutton 2040 (or other actions such as backwards swipes) brings back thehome page 700 or a previous page.

FIG. 21 shows an exemplary settings page 2100 that is opened, forexample, when the settings icon or link 790 (e.g., settings icon or“Settings” link”) on the home page 700 is selected. The settings page2100 enables a user to view and change general settings and othersettings. For example, the settings page 2100 can be used to changefonts, languages, display orientation, etc. via its graphical userinterface. Referring to FIG. 25D, an exemplary scrolling text fonts page2530 is shown with a preview pane 2535 that enables the viewing and/orselection of different fonts such as, for example, rounded, condensed,boxed, and other font choices that are not shown. By a swipe or othergesture on a screen, for example, other font choices can be viewed.Further, the option of all text being in capitals is provided. Thepreview pane 2535 can also be a pop-up window or a separate page. Thepreviewed pane 2535 can also illustrate various changes in fonts on arepresentation of a selected model of the mobile device cover 100.Further, the previewed display can also be actually displayed on themobile device cover 100 to view the display (e.g., scrolling textdisplay) in view of any font changes, for example. Referring to FIG.25E, an exemplary scrolling orientation page 2550 is shown with apreview pane 2555 that enables the viewing and/or selection of differentorientations (e.g., whether the text scrolls up, down, left, right,whether the text is in landscape or portrait format, etc.) for thescrolling text. The preview pane 2555 can also be a pop-up window or aseparate page. The previewed pane 2555 can also illustrate variouschanges in orientation on a representation of a selected model of themobile device cover 100. Further, the previewed display can also beactually displayed on the mobile device cover 100 to view the display(e.g., scrolling text display) in view of any orientation changes, forexample. Some embodiments provide that the host mobile device 110 and/orthe mobile device cover 100 can determine, for example, whether the hostmobile device 110 and/or the mobile device cover 100 is upside down orsome other orientation, for example, via an internal gyroscope and/oraccelerometer, for example, and automatically re-orient the displayedinformation accordingly so that the displayed information is easily readby a user.

Referring back to FIG. 21, respective icons 2110 (e.g., graphicalswitches or graphical elements that can be selected or toggled) areselected to turn on or off corresponding categories of notifications.For example, phone notifications, message notifications, emailnotifications, alerts, application notifications, or other notificationssupported and displayed on the mobile device cover 100 and/or the hostmobile device 110 can be turned on or off. Further, by selecting an iconor link 2120, 2130, 2140 on the settings page 2100, anotifications-for-applications page 2200, a lightshows-for-contacts page2300, a synchronization/reset page 2400, etc. can be opened. Thesettings page 2100 also provides icons or links 2150, 2160 that open anabout page, a test functions page, and other settings pages. The aboutpage enables the user to view model or version details of the mobileapplication and/or the mobile device cover 100. In addition, an icon orlink 2170 is provided to facilitate the update of the mobile applicationon the host mobile device 110 and/or the mobile device cover 100, andthe software and/or circuitry on the mobile device cover 100. Selectingthe back button 2180 (or other actions such as backwards swipes) bringsback the home page 700 or a previous page.

FIG. 22 shows an exemplary notifications-for-applications settings page2200 according to an embodiment of the present disclosure that isopened, for example, when the notifications-for-applications icon orlink 2120 on the settings page 2100 is selected. Thenotifications-for-applications settings page 2200 enables a user to viewand make changes (e.g., generally or specifically) to parametersgoverning the display of application notifications on the mobile devicecover 100. Referring to FIG. 22, various parameters can be set by theuser. For example, the user can generally (or specifically) enable ordisable, via a graphical switch 2210, the application notificationsbeing shown on the mobile device cover 100 for phone notifications,message notifications, email notifications, application notifications,etc. When enabled, the user can then set other general or specificparameters for the application notifications. Thenotifications-for-applications settings page 2200 provides the user withan icon 2220 (e.g., graphical switch or graphical element that can betapped or toggled) that causes icons (e.g., icons, emojis, graphicaldesigns, animations, lightshows, light icons, scrolling text, etc.) tobe included or not included during an application notification displayedon the mobile device cover 100. Other parameters for general or specificapplication notifications that a user can view and modify includeturning on/off animations 2230 and/or text scrolling, and setting ascroll speed 2240, a type of separator 2250 between text and/or icons, anumber of repeat times 2260, etc. Selecting the back button 2270 (orother actions such as backwards swipes) brings back the home page 700 ora previous page (e.g., the settings page 2100).

FIG. 23 shows an exemplary lightshows-for-contacts settings page 2300according to an embodiment of the present disclosure that is opened, forexample, when the lightshows-for-contacts icon or link 2130 on thesettings page 2100 is selected. The lightshows-for-contacts settingspage 2300 enables a user to view and make changes (e.g., generally orspecifically) to parameters governing the display of contact lightshowson the mobile device cover 100. Referring to FIG. 23, various parameterscan be set by the user. For example, the lightshows-for-contactssettings page 2300 provides a sort order icon or link 2310 (e.g., thatprovides a pop up menu) that is selected to set a sorting parameter forcontacts (e.g., a list of contacts) in the mobile application, and adisplay order icon or link 2320 that is selected to set a displayparameter for contacts (e.g., first name before last name when a contactis displayed on the mobile device cover 100). Further, the lightshows,icons (e.g., light icons), scrolling text, etc. for the phone, message,email, etc. are enabled or disabled by icons 2330 (e.g., graphicalswitches or graphical elements that can be selected or toggled). Inaddition, content can be displayed on the mobile device cover 100including, for example, phone numbers, email addresses, transcriptionsof voice mails, the body of emails, the body of texts, attachments tothe emails or texts, etc. Different parameters can be generally be setfor the different types of communication, for example, to distinguishthem from each other. For example, once a particular category ofapplication notification has been enabled, animations can be turned onor off (e.g., via graphical switch 2340), particular animations can bechosen, and other animation characteristics (e.g., blink, fade, etc.) ofthe animations can be set (e.g., via menus links 2450, 2460) for thegeneral categories such as notifications for phone, messages, emails,etc. or for specific phone numbers, messages/emails from specificsenders, etc. In some embodiments, animations and animation parameterscan be set for groups (e.g., subsets) of contacts depending upon thetype of communication. Selecting the back button 2470 (or other actionssuch as backwards swipes) brings back the home page 700 or a previouspage (e.g., the settings page 2100).

FIG. 24 shows an exemplary synchronization/reset page 2400 that isopened, for example, when the synchronization/reset icon or link 2140 onthe settings page 2100 is selected. By selecting the reset-to-defaulticon or link 2410, the synchronization/reset page 2400 enables the userto reset the mobile application settings to original default values andclear contact lists and other information in the mobile application. Thedefault values and other information are sent to and/or stored in themobile device cover 100 and/or the host mobile device 110. By selectingthe sync-settings-with-case icon or link 2420, the synchronization/resetpage 2400 enables the user to synchronize the mobile application withthe mobile device cover 100, for example, by sending presentvalues/settings and other present information (e.g., present settings,contact lists, selected animations, icons, parameters, etc.) to themobile device cover 100 or vice versa. Further, by selecting therepair-LED-grid icon or link 2430, the synchronization/reset pageenables a rewrite of all sectors for the mobile device cover 100,including sectors that store light patterns, light shows, fonts, icons,animations, clock faces, graphical elements, graphical designs, etc. Thesynchronization/reset page 2400 also provides an icon or link 2440 forbacking up settings and/or other information to a cloud network. Themobile application also provides an icon 2450 for restoring settingsand/or other information of the mobile application and/or mobile devicecover 100 from settings and/or other information stored on the cloudnetwork. In some embodiments, selections made on thesynchronization/reset page 2400 include warnings about the informationbeing lost if the user proceeds with the synchronization, reset, repair,and/or restore. For example, resetting or synchronizing the mobileapplication and/or the mobile device cover 100 can cause the settingsand lookup tables (or other types of memory or storage) in the mobiledevice cover 100 to be overwritten. Selecting the back button 2460 (orother actions such as backwards swipes) brings back the home page 700 ora previous page (e.g., the settings page 2100).

Some embodiments of the mobile device cover 100 according to the presentdisclosure run and/or support a same operating system or a differentoperating system as the operating system that is running and/orsupported on the host mobile device 110. For instance, in an exemplaryembodiment, the host mobile device 110 runs and/or supports the sameoperating system iOS, for example, as the mobile device cover 100. Inother exemplary embodiments, the host mobile device 110 runs and/orsupports iOS or macOS, while the mobile device cover 100 runs and/orsupports one or more of the following: an Android operating system, aBlackBerry operating system, a Symbian operating system, a Palmoperating system, a webOS, a Windows Phone operating system, a Windowsoperating system, a Linux operating system, Unix-type operating systems,Solaris operating system, AmigaOS, etc. It is within the scope of thepresent disclosure that the host mobile device 110 and/or the mobiledevice cover 100 run and/or support one or more of the listed operatingsystems as well as other operating systems.

In some embodiments in which the mobile device cover 100 runs and/orsupports a different operating system than the host mobile device 110,the mobile device cover 100 can install and run particular applicationsthat run on one operating system, but not the other, or can run on both.For example, in an exemplary example in which the host mobile device 110runs iOS and the mobile device cover 100 runs the Android operatingsystem, Android applications can be installed and run on the mobiledevice cover 100 that cannot be installed on iOS of the host mobiledevice 110. Since there are some applications that only have an Androidversion and not an iOS version, the mobile device cover 100 enables theuser to use the Android-compatible applications even if the host mobiledevice 110 runs iOS. It is also within the scope of the presentdisclosure that an application that has both an Android version and aniOS version, for example, be installed separately on the host mobiledevice 110 and the mobile device cover 100. In addition, the mobiledevice cover 100 can support the look-and-feel and operation of anAndroid smartphone, for example, while the host mobile device 110 cansupport the look-and-feel and operation of an iOS smartphone, forexample.

According to some embodiments of the present disclosure, whether thehost mobile device 100 and/or the mobile device cover 100 run and/orsupport the same operating system or different operating systems (e.g.,different mobile operating systems or other types of operating systems),the mobile device cover 100, the host mobile device 110, and/or themobile application operate, as described herein, including, for example,displaying notifications, controlling the mobile device cover 100 and/orthe host mobile device 110, and performing other functions and/orfeatures as disclosed in the present disclosure. Further, the mobiledevice cover 100 can also support its own applications separately fromthe mobile application and/or other applications running on the hostmobile device 110 that can be accessed by the mobile device cover. Anexemplary home screen 2600 of the mobile device cover 100 as shown inFIG. 26 shows applications that are installed on the OS of the mobiledevice cover 100 and can be run and/or supported separately on themobile device cover 100 by tapping or toggling an application icon 2610.It is also within the scope of the present disclosure that the exemplaryhome screen 2600 also includes icons and/or applications that areinstalled on the host mobile device 110 and accessible by the mobiledevice cover 100.

Some embodiments of the mobile device cover 100 according to the presentdisclosure provide that the mobile phone cover 100 provide its owncommunications hardware (e.g., wired and/or wireless transceivers,wireless and/or radio frequency communication circuitry, infraredfrequency communication circuitry, near-field communication circuitry,microwave frequency communication circuitry, wireless local area networkcommunication circuitry, Bluetooth communication circuitry, processors,frequency upconverters, frequency downconverters, analog-to-digitalconverters, digital-to-analog converters, amplifiers, filters, signalconditioners, antennas, etc.) and/or data, code, instructions, firmware,and/or software executable by the communications hardware so that it canwirelessly communicate independently of the host device cover 110. Forexample, as noted above, the mobile phone cover 100 can include a SIMcard. The SIM card can be inserted in and/or integrated with the mobiledevice cover 100 that can include, for example, an identification numberand security mechanisms (e.g., a security key) that are used tofacilitate wireless communication (e.g., cellular communication,satellite communication, etc.) and to prevent operation if removed. Insome embodiments, the SIM card is used to identify and/or authenticate asubscriber to a particular communication system to facilitate cellularcommunication for a particular cellular provider, for example. DifferentSIM cards can be inserted in the mobile device cover 100 to change theconfiguration of the wireless communications for a different phonenumber, wireless communication provider, communication standard,security protocol, etc. With an extra SIM card, two phone numbers can beutilized by the host mobile device 110 and the mobile device cover 100.For example, the host mobile device 100 can have a first phone numberthat be used for work, and the mobile device cover 110 can have a secondphone number that can be for personal use.

By selecting the mobile device cover phone icon 2620 as shown on thehome screen 2600 of the mobile device cover as shown in FIG. 26, themobile device cover 100 can operate as its own communication device(e.g., wireless communication device, cellular phone, text communicationdevice, message communication device, video/multimedia communicationdevice, etc.). In some embodiments, the mobile device cover 100 canoperate as its own communication device without using the communicationhardware (e.g., cellular hardware, wireless communication hardware,etc.) of the host mobile device 110. It is also within the scope of thepresent disclosure that the mobile device cover 100 wirelesslycommunicate (e.g., make or receive a call, transmit or send an email ortext message, etc.) using the communication hardware of the host mobiledevice 110. Further, the mobile device cover 100 can operate as its owncommunication device without using the communication hardware of thehost mobile device 110 independent of whether the mobile device cover100 and the host mobile device 110 run and/or support the same operatingsystem or different operating systems.

By selecting the mobile device cover phone icon 2620 as shown on thehome screen 2600 of the mobile device cover as shown in FIG. 26, anexemplary mobile device cover phone page 2700 is opened as shown in FIG.27. Although illustrated with graphical buttons 2710 for dialing a phonenumber, the home screen 2600 can also display a contact list that can beused to facilitate making a phone call, sending an email or a text,initiating a video/multimedia call, posting on a contact's social mediawebpage, etc. Referring to FIG. 27, the mobile phone cover 100 alsoincludes a microphone 2720 and a speaker 2730. In some embodiments, themicrophone and speaker of the host mobile device 110 can be used.

In some embodiments, the host mobile device 110 and the mobile devicecover 100 can share use of devices and/or peripherals (e.g., screens,microphones, cameras, speakers, gyroscopes, accelerometers, wired and/orwireless transceivers, etc.). These devices and/or peripherals can beused by the mobile applications and/or the operating systems of the hostmobile device 110 and/or the mobile device cover 100. For example, amobile application running on the host mobile device 110 can bedisplayed on a screen of mobile device cover; sound can be output toheadphones connected wiredly or wirelessly to the mobile device cover100; a microphone on the mobile device cover 100 can interact the mobileapplication running on the host mobile device 110; and/or inputs for themobile application can come from both the mobile device cover 100 andthe host mobile device 110.

Some embodiments of the mobile phone cover 100 provide that the mobilephone cover 100 be assigned its own cellular phone number, with orwithout a SIM card installed. Accordingly, a phone call can be receivedor made concurrently on the host mobile device 110 and the mobile phonecover 100. Further, while the host mobile device 110 is running anapplication (e.g., playing a movie on a player application), the mobilephone cover 100 can be physically detached, for example, and can be usedas a separate wireless communication device to make or receive, forexample, a cellular call under its own cellular phone number using itsown cellular hardware (or using the cellular hardware on the host mobiledevice 110). In some embodiments, the mobile phone cover 100 can operateas a communication independent of the host mobile device 110.

Although some embodiments provide a host mobile device 110 incommunication with a mobile device cover 100 that has a visual outputsuch as lights or a screen (e.g., a high resolution screen), someembodiments provide different configurations. For example, in someembodiments, instead of the mobile device cover 100 having or using itsown screen, the mobile device cover 100 uses the screen of the hostmobile device 110.

In some embodiments, the mobile application runs on the host mobiledevice 110 without a mobile device cover 100. The notifications, forexample, are displayed on the screen of the host mobile device 110. Insome embodiments in which the host mobile device 110 has multiplescreens and is without a mobile device cover 100, the mobile applicationcan control any or all of the screens and can switch the operatingsystem from screen to screen and vice versa. The mobile application cancontrol one of the screens of the host mobile device 110 to shownotifications, for example, and control another of the screens of thehost mobile device 110 to be the main display of the host mobile device110. Such assignments and/or functionality can be switched ortransferred among the screens of the host mobile device 110.

In some embodiments, the host mobile device 110 and the mobile devicecover 100 each have one or more screens. The mobile application has theability to control any of the screens and can switch the operatingsystem from screen to screen and vice versa. The mobile application canoverride the use of any of the screens of the mobile device cover 100and/or the host mobile device 110. The mobile application can dedicateone or more screens for notifications, and/or can prohibit one or morescreens from receiving notifications. The mobile application cantransfer the display on the screen of the host mobile device 100 to thescreen of the mobile device cover 100, or vice versa. Notifications canbe transferred by the mobile application from the screen of the mobiledevice cover 100 to the screen of the host mobile device 110, or viceversa.

Other embodiments of the present disclosure may provide a non-transitorycomputer readable medium and/or storage medium, and/or a non-transitorymachine readable medium and/or storage medium, having stored thereon, amachine code and/or a computer program having at least one code sectionexecutable by a machine and/or a computer, thereby causing the machineand/or computer to perform the steps as described herein.

Accordingly, aspects of the present disclosure may be realized inhardware, software, or a combination of hardware and software. Thepresent disclosure may be realized in a centralized fashion in at leastone computer system or in a distributed fashion where different elementsare spread across several interconnected computer systems. Any kind ofcomputer system or other apparatus adapted for carrying out the methodsdescribed herein is suited. A typical combination of hardware andsoftware may be a general-purpose computer system with a computerprogram that, when being loaded and executed, controls the computersystem such that it carries out the methods described herein.

Aspects of the present disclosure may also be embedded in a computerprogram product, which comprises all the features enabling theimplementation of the methods described herein, and which when loaded ina computer system is able to carry out these methods. Computer programin the present context means any expression, in any language, code ornotation, of a set of instructions intended to cause a system having aninformation processing capability to perform a particular functioneither directly or after either or both of the following: a) conversionto another language, code or notation; b) reproduction in a differentmaterial form.

While the present disclosure has been described with reference tocertain embodiments, it will be understood by those skilled in the artthat various changes may be made and equivalents may be substitutedwithout departing from the scope of the present disclosure. In addition,many modifications may be made to adapt a particular situation ormaterial to the teachings of the present disclosure without departingfrom its scope. Therefore, it is intended that the present disclosurenot be limited to the particular embodiment disclosed, but that thepresent disclosure will include all embodiments falling within the scopeof the appended claims.

What is claimed is: 1-20. (canceled)
 21. A mobile phone accessory, themobile phone accessory comprising: a visual output device; and aprocessor that operates an Android operating system, wherein theprocessor is operable to display information received from a mobilephone on the visual output device, and wherein the mobile phoneaccessory is separate from the mobile phone.
 22. The mobile phoneaccessory according to claim 21, wherein the information received fromthe mobile phone comprises information relating to one or more of aphone call, a video call, an email, a text message, and a video.
 23. Themobile phone accessory according to claim 21, wherein the informationreceived from the mobile phone comprises information received from asocial media application.
 24. The mobile phone accessory according toclaim 21, wherein the mobile phone accessory is in wirelesscommunication with the mobile phone via one or more of a Bluetooth link,an IEEE 802.11 link, a WiFi link, and a wireless local area networklink.
 25. The mobile phone accessory according to claim 21, wherein themobile phone accessory is operable to make one or both of a cellularphone call and a video phone call.
 26. The mobile phone accessoryaccording to claim 21, wherein the mobile phone accessory and the mobilephone are assigned different cellular phone numbers.
 27. The mobilephone accessory according to claim 21, comprising: a speaker; amicrophone; and one or more radio frequency (RF) wireless transceivers,wherein the speaker, the microphone, and the one or more RF wirelesstransceivers are operatively coupled to the one or more processors. 28.The mobile phone accessory according to claim 21, wherein the wirelesscommunication hardware comprises cellular communication hardware andwireless communication hardware that supports one or more of WiFicommunication, IEEE 802.11 communication, wireless local area networkcommunication, and Bluetooth communication.
 29. The mobile phoneaccessory according to claim 21, wherein the mobile phone accessory isoperable to display streaming video received via the mobile phone. 30.An accessory for use with a mobile phone running an iOS operatingsystem, the accessory being separate from the mobile phone, theaccessory comprising: a video output device; and a processor running anAndroid operating system to provide cellular communication, wherein theprocessor is operable to display information received from the mobilephone on the video output device.
 31. The accessory according to claim30, wherein the information received from the mobile phone comprisesinformation relating to one or more of a phone call, a video call, anemail, a text message, and a video.
 32. The accessory according to claim30, wherein the information received from the mobile phone comprisesinformation received from a social media application.
 33. The accessoryaccording to claim 30, wherein the accessory is in wirelesscommunication with the mobile phone via one or more of a Bluetooth link,an IEEE 802.11 link, a WiFi link, and a wireless local area networklink.
 34. The accessory according to claim 30, wherein the accessory isoperable to make one or both of a cellular phone call and a video phonecall.
 35. The accessory according to claim 30, wherein the accessory andthe mobile phone are assigned different cellular phone numbers.
 36. Theaccessory according to claim 30, comprising: a speaker; a microphone;and one or more radio frequency (RF) wireless transceivers, wherein thespeaker, the microphone, and the one or more RF wireless transceiversare operatively coupled to the one or more processors.
 37. The accessoryaccording to claim 30, wherein the wireless communication hardwarecomprises cellular communication hardware and wireless communicationhardware that supports one or more of WiFi communication, IEEE 802.11communication, wireless local area network communication, and Bluetoothcommunication.
 38. The accessory according to claim 30, wherein theaccessory is operable to display streaming video received via the mobilephone.
 39. A mobile phone accessory for use with a mobile phone runningan iOS operating system, the mobile phone accessory being separate fromthe mobile phone, the mobile phone accessory comprising: a video outputdevice; cellular hardware; and a processor operatively coupled to thecellular hardware and the video output device, wherein the processor isoperable to display information received from the mobile phone on thevideo output device, and wherein the processor is operable to operate anAndroid operating system to provide cellular communication via thecellular hardware, and wherein the mobile phone accessory is assigned adifferent phone number than the mobile phone.
 40. The mobile phoneaccessory according to claim 39, wherein the mobile phone accessory andthe mobile phone are operable to be in wireless communication with eachother.